Russ and I discussed this as a way to give David access to finalize the meeting in the app. This is one area where I don't like that we tied the data to meetup and I'm hesitant to have meetup drive titles and roles. Let's discuss this in more detail at the next organizer meeting.

I'm also in favor of removing the setting of user roles within the topics app to anything provided by meetup.org. The only thing we should use meetup.org for is "member" registration and authentication. The role of a user within the app is their authorization, which is something that should be entirely within our control.

Russ's commit is a quick, band-aid fix, but points out an area within the app that definitely needs some attention...

I agree and disagree. I don't like the idea of having a direct tie to Meetup, but I would like to make this a general purpose app so other groups could possibly use it.

So with that said, there are 2 solutions that I can see. Either keep the link that checks the role of the user or have an admin section where we can designate users that have admin privileges.

I'm fine with either solution. The one liner is a quick and easy fix.

On Sep 25, 2013, at 10:05 AM, "Brian V. Hughes" notifications@github.com wrote:

I'm also in favor of removing the setting of user roles within the topics app to anything provided by meetup.org. The only thing we should use meetup.org for is "member" registration and authentication. The role of a user within the app is their authorization, which is something that should be entirely within our control.

Russ's commit is a quick, band-aid fix, but points out an area within the app that definitely needs some attention...

—
Reply to this email directly or view it on GitHub.

When you are writing an app that you will run/control, bootstrapping admin privileges is usually easy enough. Just make a seed for it or hop on console and just make an update. When writing an app that others will run/control either fully or through some kind of multi-tenancy, it gets trickier.

Meetup gives a good way to bootstrap this with the organizer list, but I don't think the organizer list should be the thing that is checked for admin privileges. That is to say, when an account is created in the app using "sign in with Meetup" then the "admin flag" should be flipped on if that person is an organizer for the group on Meetup. The flag then is what is checked moving forward. The organizer check would only be made on first account creation.

Then an admin should be able to edit another user either through an admin area or some other means to flip the admin flag on/off. Finally we add a rule that if you are an admin you can't remove your own admin flag. This ensures there is always at least one admin.